## Summary
Independent follow-up to merged #579, based on
`5ac67ce6dc78dd24c2d0e766bd9b07c1f161721a`. No production locator,
production wait/shutdown semantics, coverage comparator, workflow,
tolerance, workload, or performance lane is changed.
- Replace the duplicated ARM64 substring exclusion in the functional
test with one comparison helper. Only `MacPythonOrg` aliases matching
`/Users/runner/hostedtoolcache/Python/<major.minor.patch>/{x64,arm64}/bin/python`
qualify, and each must resolve to that environment's executable before
exclusion on either side. Different/missing targets fail; ordinary
aliases and metadata comparison remain intact. Focused cases cover both
architectures, unrelated/malformed paths, non-ASCII/non-UTF8 components,
and different/broken targets.
- Make cache owner/value/None/panic tests observe an actual pending
waiter before publication. The instance-local observation is
`cfg(test)`-only and bounded; the existing owner guard still wakes
waiters on unwind.
- Make output tests observe the initial empty-queue wait for each writer
instantiation, and signal blocking test writers/serialization while
holding their release mutex. Test-only observations cannot be overtaken
by send/close/release; production remains unchanged.
- Exercise descendant-termination polling while a real file lease is
held until the pending poll is observed. Document these comparison and
synchronization contracts.
## Controlled native evidence
The merged-main Intel failure independently reproduces the extra x64
toolcache alias: [run 43978821541 / job
133689660257](https://github.com/microsoft/python-environment-tools/actions/runs/43978821541/job/133689660257).
Before changing coverage behavior, [run 43981161006, attempt
1](https://github.com/microsoft/python-environment-tools/actions/runs/43981161006)
measured **the same unchanged main commit** in two separate
source/target trees in predeclared A/B/B/A order. Artifact
**14283815268**, `macos-aa-43981161006-1`, retains full LLVM JSON with
function/instantiation regions, LCOV, repeated exports, raw profiles,
contexts, and isolated child proof.
| Measurement | A1 | B1 | B2 | A2 |
| --- | ---: | ---: | ---: | ---: |
| Unchanged main LH / LF | 18146 / 22512 | 18146 / 22512 | 18149 / 22512
| 18146 / 22512 |
| Patched LH / LF | 18202 / 22563 | 18202 / 22563 | 18202 / 22563 |
18201 / 22563 |
The unchanged **same-path B1/B2** comparison fails at -0.013pp.
Re-exporting the same profiles is byte-identical in every pass. LLVM
regions identify cache waiter paths and `writer_loop<FailingWriter>`
scheduling-dependent hits; a positive union of `DA` lines hides the
latter instantiation difference. This establishes runtime path
variability in this experiment, not a compiler/exporter defect or a
revision-dependent regression. Original artifact **14275796507**
separately identifies the descendant lease's three missed pending-poll
lines.
[Patched run 43983235000, attempt
1](https://github.com/microsoft/python-environment-tools/actions/runs/43983235000),
artifact **14284656224**, `macos-aa-43983235000-1`, passes all four
predeclared raw comparisons. Cache and output summaries are identical
across its four passes. Residual spread is one test-helper line
(0.0044pp), retained without normalization and below the **unchanged
0.01pp** gate. Function totals are constant within each experiment: main
1826/2205; patched 1829/2208.
Both experiments use Rust 1.100.0 / LLVM 23.1.5 / cargo-llvm-cov 0.9.1
on native ARM64 macOS. Every isolated subprocess proof remains idle=0 /
info=1 at handler, transport, and writer. Temporary dispatch-only
experiment changes were removed completely from the final diff.
## Review and validation
- Thorough independent custom **Reviewer** review of the final five-file
patch: **LGTM, no actionable high-confidence bugs**; specifically
examined alias scope, lock ordering, bounded observations, unwind
cleanup, platform gating, and coverage integrity.
- Affected Windows library tests: 157 passed; local alias path
regressions: 2 passed. The malformed-ARM64 retention case failed with
the old substring implementation before the fix.
- Required `cargo fmt --all` and `cargo clippy --all -- -D warnings`,
additional changed-package test-target Clippy, and 17 workflow-contract
tests passed.
- Four complete native default-feature workspace measurements of the
patched Rust source passed, including Unix filesystem identity cases and
subprocess proof.
### Hosted PR validation at `cc3379ba77b7e5221b72824f9d8a560d4802424c`
All six repository workflows passed on their first PR attempt, as did
the external policy check:
| Validation | Evidence | Result |
| --- | --- | --- |
| Native Intel and ARM64 installed-manager tests, both native builds,
full functional matrix | [PR/CI Check
43984292297](https://github.com/microsoft/python-environment-tools/actions/runs/43984292297);
Intel job `133708333703`, ARM64 job `133708333963` | Pass; original
Intel `verify_validity_of_discovered_envs ... ok`, its suite 6 passed /
0 failed |
| Native exact-main raw coverage and isolated child proof | [Native
coverage
43984292202](https://github.com/microsoft/python-environment-tools/actions/runs/43984292202),
artifact **14284442352** | Pass; HEAD 18201/22563 lines and 1829/2208
functions vs main 18146/22512 and 1826/2205; **+0.062pp lines / +0.023pp
functions**, isolated witnesses idle=0/info=1 |
| Linux and Windows exact-base coverage/context gates | [Coverage
43984292251](https://github.com/microsoft/python-environment-tools/actions/runs/43984292251)
| Pass |
| All four performance lanes, including native Intel and ARM64 macOS |
[Performance
43984292229](https://github.com/microsoft/python-environment-tools/actions/runs/43984292229)
| Pass |
| Three-platform Clippy and session benchmarks | [Lint
43984292357](https://github.com/microsoft/python-environment-tools/actions/runs/43984292357),
[benchmarks
43984292289](https://github.com/microsoft/python-environment-tools/actions/runs/43984292289)
| Pass |
| External PR/signing policy | [VS Code PR
Check](https://github.com/microsoft/vscode-engineering/actions/runs/43987471692)
| Pass |
All commits are locally GPG-signed and GitHub-verified. No merge or
auto-merge is enabled; no merge is requested or authorized.
---------
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Summary
$CONDAis preinstalled, without creating or activating an extra environment. Repair both PR workflows and baseline publishers.macos-15-intel. Match Conda installers to native architecture and retain both architectures' functional/build coverage.scripts/quality_measurement.pyand adding a distinct native ARM64 lane to both performance workflows while retaining Intel.Root cause and impact
Before this repair, Linux jobs failed before testing because Ubuntu 26.04 no longer supplied the Conda installation assumed by the workflows. The cancelled macOS jobs never received a runner: their macOS 14 configuration retired on November 2.
The original Windows numerical coverage failure compared Rust 1.99.1/LLVM 23.1.1 with Rust 1.100.0/LLVM 23.1.5 and different runner images. With the same 96 Rust source files, LCOV denominators changed from LF 23,480/FNF 2,231 to LF 23,288/FNF 2,254. This demonstrates measurement-environment drift, not that the compiler alone explains every changed hit.
The original macOS startup-P95 outlier is not treated as a proven product defect. Its one unchanged-head rerun passed the timing budgets but failed inventory matching: 12 environments versus the historical baseline's 11. Fresh comparisons address that comparability problem without discarding slow samples or normalizing inventories away.
Preserved invariants and review follow-up
helper_revisionand the measured source SHA are validated separately; head Rust source/binaries are never substituted for the base.quality_snapshot.py.Current validation
Current head:
f10594fd644f112fa609dce548feab29d0dd4c92, a new locally GPG-signed commit preserving parent31901b8. Both local GnuPG verification and GitHub's OpenPGP verification succeed. The trusted-team-key signing policy recognizes the signature;VS Code PR Checknow passes with the required collaborator approval.Actual measurements use exact base
02dd29e49e3c71d4ec06e1072d6331494a12e01dand tested merged6d49a1ad7080a4e9bcda6259cd60a11fa3ab384containing the current head.Remaining CI blockers
The review changes are pushed and all four reviewer threads have replies and are resolved, but the PR is not fully green:
verify_validity_of_discovered_envsatci_test.rs:629: full discovery includes one additional hosted-toolcache x64 Python symlink that directtry_fromdoes not return. Interpreter identity/version/prefix/manager/architecture agree. Existing CI normalization excludes ARM64 toolcache aliases but not x64. The initial repair passed on the same image/Python version; why the extra alias appears in this run remains unproven. This follow-up changes neitherpr-check.ymlnor Rust and that job does not invoke the helper. No product-locator workaround or blanket retry was made.These remaining reliability/alias-causality issues are reported explicitly rather than weakening gates or silently expanding the maintenance-feedback fix.